Script Editor
When a CygNet Studio screen is in Run mode, it is continuously handling events, such as object initializations, button clicks, keyboard input, and timer events. Using the script editor, script can be added to a number of events, enabling the screen to process customized logic when an event fires. Script can be written intermittently while building the screen, or it can be deferred until most of the objects are in place, depending on your preference.
Basic screens may not require scripting aside from assigning events to buttons and text boxes. However, the more familiarity you have with the properties, methods, and events of CygNet Studio objects and the scripting libraries, the more versatile your screens can become.
CygNet Studio uses the VBScript language for scripting. Refer to the specification on the Microsoft website at https://www.microsoft.com/scripting for information if you are not familiar with this language. See the CygNet Scripting Guide for more information about scripting in general.
The Scripting reference libraries available for use in CygNet Studio are described in the Scripting section of this Online Help document.
Note: The SCRADMIN (Screen Admin Examples), SCRDIAGS (Screen Diagnotic Examples), and SCREXAMP (Screen Examples) folders in the APPS contains many sample screens and script. Be sure to browse through these files to familiarize yourself with how scripting is commonly added to object events.
Note: CygNet Studio screens can be viewed in the application’s companion product, CygNet Vision. CygNet Vision is a run-time version of Studio. The script and properties of screens cannot be edited in Vision.
Note: Job Runner is a multi-threaded execution environment for VBScript and .NET assembly methods that can significantly improve performance in HSS scripts and CygNet Studio screens. See Job Runner for more information.
More:
Optimizing Facility and Point Cache Usage
|
|
|
